Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update k8s.io to v0.29.12 #470

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

openstack-k8s-ci-robot
Copy link

@openstack-k8s-ci-robot openstack-k8s-ci-robot commented Nov 23, 2024

This PR contains the following updates:

Package Type Update Change
k8s.io/api require patch v0.29.10 -> v0.29.12
k8s.io/apiextensions-apiserver indirect patch v0.29.10 -> v0.29.12
k8s.io/apimachinery require patch v0.29.10 -> v0.29.12
k8s.io/client-go require patch v0.29.10 -> v0.29.12
k8s.io/client-go indirect patch v0.29.10 -> v0.29.12
k8s.io/component-base indirect patch v0.29.10 -> v0.29.12

Release Notes

kubernetes/api (k8s.io/api)

v0.29.12

Compare Source

v0.29.11

Compare Source

kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)

v0.29.12

Compare Source

v0.29.11

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

v0.29.12

Compare Source

v0.29.11

Compare Source

kubernetes/client-go (k8s.io/client-go)

v0.29.12

Compare Source

v0.29.11

Compare Source

kubernetes/component-base (k8s.io/component-base)

v0.29.12

Compare Source

v0.29.11

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@openshift-ci openshift-ci bot requested review from eharney and viroel November 23, 2024 05:47
Copy link
Contributor

@fmount fmount left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Nov 27, 2024
@fmount fmount requested a review from ASBishop November 27, 2024 12:40
@openstack-k8s-ci-robot openstack-k8s-ci-robot changed the title Update k8s.io to v0.29.11 Update k8s.io to v0.29.12 Dec 14, 2024
@openshift-ci openshift-ci bot removed the lgtm label Dec 14, 2024
Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

New changes are detected. LGTM label has been removed.

Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fmount, openstack-k8s-ci-robot
Once this PR has been reviewed and has the lgtm label, please assign viroel for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

@openstack-k8s-ci-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/cinder-operator-build-deploy-kuttl ebdaeaa link true /test cinder-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants